Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable no database CI workflow #271

Merged
merged 1 commit into from
Dec 10, 2022

Conversation

vishal423
Copy link
Collaborator

@vishal423 vishal423 commented Dec 10, 2022

Closes #264

@sonarcloud
Copy link

sonarcloud bot commented Dec 10, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@vishal423
Copy link
Collaborator Author

I had a closer look into the generated application and it's missing a lot of things (API endpoints, In-memory user setup etc). For now, I suggest to disable this flow in CI tests and create a separate issue to track support of this advance option.

@mraible
Copy link
Contributor

mraible commented Dec 10, 2022

@vishal423 Sounds good to me. I'd prefer to get something going and iterate on it rather than trying to do everything at once.

@vishal423 vishal423 merged commit 401c6b0 into jhipster:main Dec 10, 2022
@vishal423 vishal423 deleted the nodb-cypress-issue branch December 10, 2022 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

e2e test failure in application generated using imperative-sql-jwt-maven-no-db.jdl
2 participants